Repository navigation
feat(integrations): add Vercel MCP connection - #763
aivong-openhands wants to merge 1 commit into
Conversation
Co-authored-by: openhands <openhands@all-hands.dev>
all-hands-bot
left a comment
There was a problem hiding this comment.
This review was posted by an AI agent (OpenHands).
Code change
The catalog change is correct and well-scoped. Verified on head 1cdae65:
integrations/catalog/vercel.jsonadds aprovider: mcpoption withtransport.kind: shttpand URLhttps://mcp.vercel.com- the shape the MCP library requires. It edits exactly one hand-authored JSON file underintegrations/catalog/, so it respects the repository's single-source-of-truth rule and introduces no parallel provider/runtime files.npm run build:integrationsproduces no diff againstintegrations/catalog-index.js(confirmed locally), so no regeneration is needed.tests/test_integration_catalog_in_sync.py,tests/test_catalog_schema.py, andtests/test_catalogs.pypass on this head (116 passed).https://mcp.vercel.com/.well-known/oauth-authorization-serveradvertisesregistration_endpointandtoken_endpoint_auth_methods_supported: ["none"], so dynamic client registration with no client secret is supported. The unauthenticated endpoint returns401, as expected.oauth.clientAuthentication: "none"matches existing MCP entries in the catalog (e.g.atlassian-rovo.json,granola.json,superhuman-mail.json), so it is consistent with current convention.
No inline findings on the changed lines.
Blocking: required "Validate PR description" check is failing
The PR Description Check run for this head (run id 38263311054, pull_request_target) completed with failure, and the PR currently shows mergeable_state: blocked. The job log reports 6 errors against the current body:
- The first visible line of the PR description must be
HUMAN:. - Add a short human-written note (at least 20 characters) between
HUMAN:andAGENT:. - Keep the
AGENT:marker from the PR template. - Keep the
## Whysection from the PR template. - Keep the
## How to Testsection from the PR template. - Link an issue in the
## Issue Numbersection (e.g.Fixes #123).
The current body has only ## Summary, so the required HUMAN:/AGENT: structure and the ## Why, ## Issue Number, and ## How to Test sections are absent. Repository policy (AGENTS.md, .github/scripts/check_pr_description.py, .github/pull_request_template.md) requires those sections, plus a linked issue carrying ready-for-dev unless it predates the 2026-08-25 rollout. Please restore the template structure and human attestation and link the relevant issue, then re-run the check. The code itself is ready; this gate is the only thing standing between the change and merge.
🔄 CHANGES REQUESTED
Summary
Adds the official Vercel MCP server as a connection option on the existing Vercel integration in the catalog. Vercel already had a catalog entry with only a REST (
http) option, which the MCP library filters out, so the entry was not installable as an MCP server.Details
integrations/catalog/vercel.json:oauth-mcpconnection option:provider: mcp,transport: shttp, URLhttps://mcp.vercel.comoauth2withclientAuthentication: none. The server supports dynamic client registration and PKCE, so no client credentials are needed.oauthoption is unchanged.docsUrlnow points to the Vercel MCP docs, andnotesexplains the sign-in flow.integrations/catalog-index.jsneeds no change. It imports the JSON files, andnpm run build:integrationsproduces no diff.Validation
npm run build:integrationsleavescatalog-index.jsunchangedtests/test_integration_catalog_in_sync.py,tests/test_catalog_schema.pyandtests/test_catalogs.pypasshttps://mcp.vercel.com/.well-known/oauth-authorization-serveradvertises a registration endpoint andtoken_endpoint_auth_methods_supported: ["none"]This PR was created by an AI agent (OpenHands) on behalf of the user.
Jev-Fast-Audit
⚡ Jev fast audit · estimates · 0.19s · commit 1cdae65
Strongest signal: No primary concern selected.
Evidence: No primary concern to locate.
Coverage: complete supplied coverage; 1/1 hunks, 1/1 files.
All estimates and evidence